#

A month ago, Windows XP source code got leaked and a group of people on the internet are trying to make some weird things with it. OpenXP is basically a re-implementation of Windows NT 5.2, which was the build of NT underpinning Windows Server 2003.

OpenXP aims to integrate critical features that users have come to expect of a modern version of Windows, such as even more US government backdoors, constant telemetry, a whole lot more spaghetti code and integrated bloatware that cannot be removed from the system.

Just kidding, the goal is to eventually refactor and modernise this absolute travesty of a codebase and present to users a secure, lightweight and visually appealing (everyone loved the XP shell) operating system that is binary compatible with Windows applications, with modern conveniences that are missing from NT 5.2 such as native WPA/WPA2 support for WiFi, SSDs, UEFI boot support on x86/amd64 (XP only supports Itanium EFI) and an optimised multiprocessor scheduler.

OpenXP is currently in alpha. It is probably unstable, likely a bit janky and definitely full of security holes. Do not expect a fully working daily driver OS at this point in time. It is strongly suggested that you test out OpenXP in a VM, or if you want to install to hardware, use contemporaneous machines (2010 and older) and do not connect them to your network.

If you want network access, set up an isolated VLAN. You should know how to do this if you found your way here.

RELEASES

Coming soon (maybe)

Current list of differences from NT 5.2 source code

• No 16-bit support in user space (NTVDM/OLE16 are gone)
• EULA changed to a custom one for OpenXP
• Crap NT 5.2 'installation music' swapped out for the iconic NT 5.1 (Windows XP) 'installation music'
• Many small changes to various support files that make the build process much more streamlined

  ---

Important information for developers

This repo is the codebase from which binary releases are built. As such, it is imperative you do not make pull requests for code that has not been tested to at the very least break anything that has already been implemented. Bugs are okay, but ensure they are documented thoroughly so some enterprising individual can have a crack at squishing them.

Building the system

Build guide can be found here.

Pull request etiquette

When making a pull request, please explain in detail what and how your changes do that thing they do. Do not assume something is trivial to understand just because you found it so.

Code etiquette

The code is enough of a mess as it is. A major goal of OpenXP is to refactor/clean up the codebase to be as simple, clean and streamlined as possible. When writing your code, ensure you are following modern C/C++ conventions and please make an effort to write regular, concise comments explaining the code. One of the major problems with the code as it stands is a severe lack of documentation. Please do not compound this problem.

Most pressing matters to attend to

• Build a dependency diagram
• Get some documentation for critical system components
• GET AMD64 BUILDS WORKING
• Rework the UEFI bootloader for x86 (and amd64)
• Remove alphabet agency backdoors
• Remove MS SMB/Kerberos and implement Samba
• Implement LibreSSL as the default system SSL